FMS Legacy Configuration Data Group

The "FMS Legacy Configuration Data" (GmrConfig) data group does not retrieve data directly from a remote device; instead, it depends on another data group to supply data to it.

The "FMS Legacy Configuration" data group is defined once in a device template file, but it can be instantiated in the remote device editor and ordinalized to scale to your collection needs. You must associate each such "FMS Legacy Configuration" data group with a matching support data group. For example, if you instantiate "FMS Legacy Configuration" data group ordinal 1, you must also instantiate support data group ordinal 1.

Support data groups are assigned to an "FMS Legacy Configuration" data group in the gmrDataGroupList element of the GmrConfig data group in a device template file. Mapping between "FMS Legacy Configuration" data group elements and FMS Legacy data items is within the ConfigItems element of gmrMaps in the device template file. Optional data groups can be used to get similar data for different meter types. See also FMS Legacy Configuration Data Items.

Data Group Ordinals

The messageOrd attribute refers to the ordinal of the support data group listed in the gmrDataGroupList section of the "FMS Legacy Configuration" data group. The ordSelector attribute defines the instance of the "FMS Legacy Configuration" data group with which the support data group is associated. In the example below, messageOrd is in reference to the ordinal of GmrCfgRun1|2|3|4 and ordSelector applies to the specific instance of the "FMS Legacy Configuration" data group.

Data group ordinals must correspond to the range defined by the maxCnt attribute.

For more information, see the following subsections:

• Example
• Structure and Components
• To Configure a Support Data Group

For more information about working with device template files, see Device Template Files.

Example

Click here to see an example of the data group   <GmrConfig niceName="FMS Legacy Configuration Data" canSend="false" dgGmrMap="configItems" maxCnt="4"> <dgElements/> <uccRecvParms> <MeterId desc="Meter ID" required="false" /> </uccRecvParms> <gmrDataGroupList> <!--Required/Optional state can be modified. Any data group where dgStruct = "Signal" or "List" can be referenced.--> <!-- messageOrd: if not specified ordinal follows ordinal of GMR request otherwise it is as specified ordSelector: if not specified datagroup is created for all GMR ordinals otherwise only if it matches GMR request ordinal --> <GmrCfgRtu required="true" messageOrd="0"/> <GmrCfgAga8 required="false"/> <GmrCfgRun1 required="false" messageOrd="1" ordSelector="1"/> <GmrCfgRun2 required="false" messageOrd="1" ordSelector="2"/> <GmrCfgRun3 required="false" messageOrd="1" ordSelector="3"/> <GmrCfgRun4 required="false" messageOrd="1" ordSelector="4"/> </gmrDataGroupList> </GmrConfig>

Structure and Components

Click here to see the structure and components of the data group   <!-- Requires at least one support data group. Support data groups are user configurable for this EIE. Exactly what support data group(s) you choose depends on your unique setup and needs. --> <GmrConfig> <dgElements/> <uccRecvParms> <UISParameter/> </uccRecvParms> <gmrDataGroupList> <SupportDataGroup required="true"/> <SupportDataGroup required="false"/> </gmrDataGroupList> </GmrConfig>

To Configure a Support Data Group

1. Using a text editor or XML editor, open the device template file to which you want to add data groups.
2. In the GmrConfig section of the device template file, define a new data group.
   1. Define a gmrDataGroupList element.
   2. Define all support data groups from which you require data.
3. Define any other required data groups.
4. Validate and load your template.